Computing device with force-triggered non-visual responses

ABSTRACT

In one example, a method includes receiving, by a computing device, an indication of a detected force applied to the computing device. The method further comprises determining, by the computing device, that the detected force matches a corresponding input that the computing device associates with a corresponding function that is executable by the computing device. The method further comprises generating, by the computing device and in response to determining that the detected force matches the corresponding input and, a non-visual output based on the corresponding function.

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.14/863,912, filed Sep. 24, 2015, which is a continuation of U.S.application Ser. No. 13/732,946, filed Jan. 2, 2013, now issued as U.S.Pat. No. 9,152,247 on Oct. 6, 2015, which claims the benefit of U.S.Provisional Application No. 61/718,059, filed Oct. 24, 2012, the entirecontent of each of which is incorporated herein by reference.

BACKGROUND

Many mobile computing devices such as smartphones and tablet computershave touchscreens that provide graphical outputs and enable users toenter inputs via touch gestures and/or virtual or hardware keyboards orbuttons. Mobile computing devices may also provide audio outputs, andenable user inputs via virtual or hardware keyboards and buttons. Mobilecomputing devices may provide a variety of functions includingtelephony, email, text messaging, web browsing, etc.

Keyboard and touch gesture inputs and graphical outputs may be theprimary modes of a user's interaction with a mobile computing device. Auser may typically begin interacting with a computing device such as asmartphone or tablet computer by positioning the computing device wherethe user can view its display and can enter gesture inputs to virtualicons or keys presented at the display.

SUMMARY

In one example, a method includes receiving, by a computing device, anindication of a detected force applied to the computing device. Themethod further comprises determining, by the computing device, that thedetected force matches a corresponding input that the computing deviceassociates with a corresponding function that is executable by thecomputing device. The method further comprises generating, by thecomputing device and in response to determining that the detected forcematches the corresponding input, a non-visual output based on thecorresponding function.

In another example, a computing device includes at least one processor.The at least one processor is configured to receive an indication of adetected force applied to the computing device. The at least oneprocessor is further configured to determine that the detected forcematches a corresponding input that the at least one processor associateswith a corresponding function that is executable by the at least oneprocessor. The at least one processor is further configured to generate,in response to determining that the detected force matches thecorresponding input, a non-visual output based on the correspondingfunction.

In another example, a computer-readable storage medium includesinstructions that are executable by the at least one processor toreceive, by the at least one processor, an indication of a detectedforce applied to a computing device. The instructions are furtherexecutable by the at least one processor to determine, by the at leastone processor, that the detected force matches a corresponding inputthat the at least one processor associates with a corresponding functionthat is executable by the at least one processor. The instructions arefurther executable by the at least one processor to generate, inresponse to determining that the detected force matches thecorresponding input and by the at least one processor, a non-visualoutput based on the corresponding function.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Other features, objects, andadvantages will be apparent from the description and drawings, and fromthe claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a perspective diagram illustrating a user interacting with anexample computing device configured to generate non-visual outputs inresponse to force-based inputs in accordance with aspects of the presentdisclosure.

FIG. 2 is a schematic diagram illustrating an example mobile computingdevice configured to generate non-visual outputs in response toforce-based inputs in accordance with aspects of the present disclosure.

FIGS. 3-6 are example graphs of acceleration over time corresponding toforce-based inputs as detected by an accelerometer operatively connectedto a mobile computing device, in accordance with aspects of the presentdisclosure.

FIG. 7 depicts a computing device with graphical user interface (GUI)and outputting GUI content for a representative portion of an exampleuser configuration interface for a non-visual I/O application thatgenerates non-visual outputs in response to force-based inputs, inaccordance with aspects of the present disclosure.

FIG. 8 is a flow diagram illustrating an example process that may beperformed by a computing device to generate non-visual outputs inresponse to inputs that correspond to detected forces in accordance withaspects of the present disclosure.

The various described features are not drawn to scale and are drawn in asimplified form in which one or more features relevant to the presentapplication are emphasized. Like reference characters denote likeelements throughout the figures and text.

DETAILED DESCRIPTION

Techniques and methods are disclosed herein whereby a computing devicecan provide force-triggered non-visual responses to user inputs. In someimplementations, such responses can be output by the mobile computingdevice without the user accessing a touchscreen or keyboard, and withoutthe user having to look at or handle the computing device. Techniques ofthis disclosure can also provide new opportunities for wearablecomputing and for interacting with a device without interfering withpersonal social interaction. Techniques of this disclosure can alsoprovide device accessibility for users with sensory impairments, orwithin the context of operating a vehicle or other machine.

This disclosure is further directed to a computing device receivingacceleration-based or squeeze-based inputs and, in response, thecomputing device outputting non-visual responses, such as audio orvibration outputs. These non-visual outputs generated in response toreceiving acceleration-based or squeeze-based inputs (collectively,“force-based inputs”) can be referred to generally as force-triggerednon-visual responses. In some examples, the computing device can outputnon-visual responses while a presence-sensitive screen of the device isoff or locked. Generating force-triggered non-visual responses canenable a user to access functionality of a computing device withouthaving to go through the process of unlocking or turning on the device'sscreen, and without directly handling the computing device. A user canmake use of functions of the computing device while the computing deviceremains in the user's pocket, with the user tapping the device throughthe cloth of the user's pants, for example. A user can also tap orsqueeze a computing device to activate certain features without havingto look at the computing device, such as when the user is driving.Force-triggered non-visual responses can also serve as an accessibilityfeature for users who have a visual impairment, in some examples.

A computing device may use any force-based inputs that can be sensedthrough any type of force sensor, such as an accelerometer or acompression/squeeze sensor. A computing device may respond toforce-based inputs in the form of any input detectable by anaccelerometer, a compression/squeeze sensor, or other sensors. Theseforce-based inputs may include tapping, squeezing, shaking, or rotatingthe computing device. The computing device can also combine theseforce-based inputs with inputs from a Global Positioning System (GPS)sensor, a cellular/WiFi position sensor, a touchscreen, a light sensor,a magnetic field sensor, a near field communication (NFC) tag sensor,etc. (collectively, “non-force-based inputs”). A computing device mayrespond to a combination of force-based inputs and non-force-basedinputs to provide additional modes of interaction for responding toforce-based inputs.

As one example of a non-visual output a computing device may generate inresponse to force-based inputs, a computing device may respond to atapping input by using speech synthesis to generate a speech audiooutput. This force-triggered speech audio output may include the currenttime of day, calendar events for the day, news headlines, a weatherforecast, selected stock quotes or market indexes, or the name and phonenumber of a caller if the user taps the computing device while it has anincoming phone call, for example. The computing device may respond to aphone call conveyed over a traditional telephony network or over apacket-based network, such as by a web-based application over theInternet, for example. The computing device may provide differentresponses to different tap inputs during an incoming phone call. In oneexample, if a call is incoming, the computing device may respond to asingle tap by answering the call on speaker, respond to two taps bygenerating a speech synthesis output stating the caller's name and phonenumber, or respond to three taps by muting the incoming call, e.g., bystopping a ringing or vibrating output.

A computing device may also provide different responses to a tap inputor other force-based input subsequent to an audio or vibration outputindicating arrival of a new email, text message, or social networkingnotification. For example, a computing device may respond to differenttap inputs or other force-based inputs by generating a speech synthesisoutput identifying the sender of the message or reading the message tothe user, or generating vibration outputs or other outputs identifyingwhether the caller or message sender is on a list of high-valuecontacts. In other examples, a computing device may respond to differenttap inputs or other force-based inputs by opening an interactiveapplication using speech synthesis audio outputs in response to voiceinputs, such as for web search, map search, or road navigation.

In other examples, a computing device may generate other types ofnon-visual responses besides audio or vibration outputs in response toforce-based inputs, potentially in combination with audio or vibrationoutputs. In various examples, a computing device may respond todifferent force-based inputs by generating an output to check into alocation on a location-based app; to open a local sharing group to sharefiles or other data with other local computing devices; to start or stopa position-tracked route (with tracking by GPS, Wi-Fi navigation, etc.)in a route tracking application; to mark a location for a geocachingapp; to interact with remote control apps, such as to lock or unlock theuser's car or start the engine, or to turn the user's TV on or off; orto start an audio recorder with transcription, which might includesaving to a notepad or word processing app or opening an email app andtranscribing into an email message draft.

A computing device may have an initial default set of non-visualresponses corresponding to different force-based inputs. A computingdevice may also enable the non-visual responses it generatescorresponding to different force-based inputs to be configurable by theuser. In one example, a computing device may have an initial defaultsetting to respond to a single tap by generating a speech synthesisoutput stating the current time of day, to respond to two taps bygenerating a speech synthesis output stating remaining events for theday from a calendar application, and to respond to three taps bygenerating a speech synthesis output stating a current local weatherforecast. The computing device may provide options for a user toreconfigure the responses generated for these inputs, and to set anyother corresponding functions for input patterns to the accelerometer,compression sensor, or other force sensor, potentially also conditionalon other sensor inputs or states. An example of a computing deviceimplementing features such as those described above is shown in FIG. 1.

FIG. 1 is a perspective diagram illustrating a user 1 interacting withan example computing device 10 configured to generate non-visual outputsin response to force-based inputs in accordance with aspects of thepresent disclosure. Computing device 10 is inside the user's pocket inthis view. As shown in the example of FIG. 1, the user taps on computingdevice 10 inside the user's pocket, which computing device 10 detectsand interprets as a tap input 14. Tap input 14 may include a single tap,two or more taps, a squeeze, an oscillating acceleration indicative ofthe mobile computing device being shaken, or other pattern of force ormotion applied to computing device 10. Computing device 10 may comparethe tap input 14 with stored force-based input parameters that may beassociated with one or more corresponding functions that are executableby the mobile computing device 10.

For example, the tap input 14 may be a sequence that includes both asingle tap followed by a double tap. In this example, computing device10 may associate a single tap input with a corresponding function ofoutputting a current time using data from a clock application, whilecomputing device 10 may associate a double tap input with acorresponding function of outputting information from or about recentlyreceived emails using data from an email application. In response todetermining that the detected forces match the corresponding inputs,i.e., the stored input parameters associated with the correspondingfunctions, computing device 10 executes the corresponding functions,i.e., outputting the current time and information about recentlyreceived emails, in this example. Executing the corresponding functionsincludes the computing device 10 generating non-visual outputs based onthe corresponding functions, such as computing device 10 generatingspeech synthesis audio output 16 of the current time and withinformation about recently received emails, in this example. In otherexamples, computing device 10 may respond to a single tap or double tap,or other force-based input, by generating a speech synthesis audiooutput with information from recently received text messages using datafrom a text message application, or from recently received socialnetworking updates using data from a social networking application, forexample.

In another example, computing device 10 may interpret different inputsfrom subsequent tap inputs within a period of time after an initial tapinput or after a response to the first input by computing device 10. Forexample, the user may tap computing device 10 to enter a first input toprompt computing device 10 to generate an audio output, such as thecurrent time, then the user may enter another one or more taps within aperiod of time after the initial audio output, such as a subsequentsingle tap to prompt computing device 10 to generate an audio outputwith calendar information for upcoming appointments. These input andoutput responses may be extended such that another single tap inputwithin a certain period of time after the calendar audio output mayprompt computing device 10 to generate yet another output, such asinformation on recently received emails or current stock market data.Computing device 10 may also enable the inputs and outputs for thesesequences of force-based inputs to be user-configurable. Computingdevice 10 may define a period of time for accepting a subsequent tapinput so that it doesn't begin too quickly after a prior tap, to preventconfusion with a double tap input, and so that it doesn't extend for toolong, to prevent confusion with later, unrelated tap inputs or randommotions, in some examples.

Computing device 10 may include logic to differentiate between distincttap inputs or other force-based user inputs and ordinary motions thatare not intended as force-based user inputs intended to elicitnon-visual outputs. Computing device 10 may also use any of variousaspects of context as part of differentiating intended force-based userinputs from non-input motions. For example, computing device 10 mayrefrain from processing detected forces for generating audio outputswhen a mute switch on computing device 10 is set to mute. As anotherexample, computing device 10 may determine whether the force is appliedwhile a presence-sensitive display (not depicted in FIG. 1) that isoperatively connected to the mobile computing device is in an activatedstate or in a deactivated state, e.g., the presence-sensitive display iseither off or locked, or while a pair of headphones or other externalaudio device are plugged into an audio socket, so that computing device10 has its default audio speakers in a deactivated state.

Computing device 10 may also refrain from processing detected forces forgenerating audio outputs if computing device 10 determines that a givenoutput component such as the presence-sensitive display or the defaultaudio output system is in an activated state. In the example noted aboveinvolving a presence-sensitive display, if computing device 10determines that the force was applied while presence-sensitive displaywas in a deactivated state, computing device 10 may then, in response,execute the corresponding function and generate the non-visual output.Computing device 10 may maintain the presence-sensitive display in thedeactivated state while generating the non-visual output. In the examplenoted above involving headphones, computing device 10 may generate audiooutputs only on determining that the force was applied while headphonesare plugged into the audio socket. For example, computing device 10 maygenerate audio outputs based on text-to-speech processing of emails toread emails aloud to the user, only if headphones are plugged intocomputing device 10 at the time the user enters the appropriate tapinputs, in this example.

Computing device 10 basing its outputs in part on whether apresence-sensitive display is in a deactivated state or whetherheadphones are plugged into an audio socket are illustrative examples ofcontext-sensitive output modes. Computing device 10 may apply a varietyof other context-sensitive output modes to determine what output channelto use for outputs in response to force-based user inputs. For example,other context-sensitive output modes may include the presence or absenceof a selected Bluetooth, NFC, WiFi, or other electromagnetic signal. Invarious examples, computing device 10 may establish a communicativeconnection with a nearby car stereo system, home stereo system, or otheraudio player system via Bluetooth or other communicative link, and maysend its audio outputs via the communicative link to be output by theconnected audio system. As another example of a context-sensitive outputmode, computing device 10 may detect through one or more of anaccelerometer, WiFi networks, a GPS sensor, etc. whether it is movingwith speeds and motions characteristic of a motor vehicle, and maygenerate audio outputs based in part on detecting that a motor vehiclecontext or “driving mode” is applicable.

Various context-sensitive output modes may be combined in some examples.For example, computing device 10 may be configured to recognize aBluetooth signal from the user's own car and only begin generating audiooutputs in response to either the Bluetooth signal from the user's car,or when computing device 10 is in a moving vehicle and headphones areplugged into the audio socket. Computing device 10 may thus avoidgenerating audio outputs out loud while the user is riding a bus orlight rail. Computing device 10 may also prompt the user forconfirmation before responding with audio outputs, such as by asking,“Okay to read emails out loud?” and continuing only if it receives acertain confirmatory force-based user input in response, such as adouble tap, for example. Computing device 10 may enable each of thesesettings to be configured by the user in various examples.

Computing device 10 may therefore accept force-based user inputs andrespond by generating audio outputs or other non-visual outputs. Asanother example of a non-visual output, computing device 10 may generatevibration outputs in response to specific force-based user inputs, suchas either one or two vibrations to communicate information. For example,computing device 10 may be configured so that when the user enters aspecific force-based input, such as a set of two taps, computing device10 checks whether a certain contact to whom the user has sent a calendarinvitation in a calendar application has sent a reply to accept thecalendar invitation. Computing device 10 may be configured to respond tothis force-based input by outputting a single period of vibration if thecontact has sent a reply to accept the calendar invitation, a set of twoperiods of vibration if the contact has not yet replied, or a set ofthree periods of vibration if the contact has replied to reject thecalendar invitation, for example.

Generating vibration outputs as non-visual outputs in response to theforce-based user inputs may enable computing device 10 to provide simpleand subtle modes of user interaction that may be more practical and/orsocially convenient than entering inputs and viewing outputs on adisplay screen in some contexts. Computing device 10 may provide acapability for the user to configure force-based inputs andcorresponding non-visual outputs to involve any of a wide range ofspecific information and/or for interacting with any type of softwareapplication.

Computing device 10 may incorporate or be operatively connected to anyof a number of different sensors that may be capable of detecting forcesapplied to the computing device, such as an accelerometer, a compressionsensor, or an acoustic sensor, for example, and may use inputs from oneor multiple sensors in determining whether a detected force isconsistent with and matches a force-based input. Computing device 10 mayevaluate the properties of detected forces over time, and may applydifferent steps of filtering and processing detected forces, such as byinitially screening sensor inputs for any potentially significant forcedetection events, and performing further processing or analysis on suchpotentially significant force detection events to determine whether theymatch a stored profile for a corresponding force-based input. Computingdevice 10 may also compare potentially significant force detectionevents with other aspects of its operating context, such as whether theforce was detected during an incoming phone call that hadn't yet beenanswered, or soon after the computing device 10 had generated an alertfor an incoming text message or email, as is further described below.

Computing device 10 may be implemented in a variety of different forms,such as a smartphone, a tablet computer, a laptop, a netbook, a wearablecomputing device, or other mobile computing device, for example.Computing device 10 may also connect to a wired or wireless networkusing a network interface. Additional details of example computingdevices are described in further detail below with respect to subsequentfigures.

FIG. 2 is a schematic diagram illustrating an example mobile computingdevice 10 configured to generate non-visual outputs in response toforce-based inputs in accordance with aspects of the present disclosure.Computing device 10 in FIG. 2 is an example implementation of computingdevice 10 in FIG. 1. Computing devices of the present disclosure may beimplemented in a variety of forms, such as a smartphone, a tabletcomputing device, a wearable computing device, etc., and may includeadditional components beyond those depicted in FIG. 2 or omit one ormore of the components depicted in FIG. 2.

Computing device 10 as shown in FIG. 2 includes an accelerometer 222, acompression sensor 224, and an acoustic sensor 226, in this example.Other examples of computing devices may include any one or more of theseor other sensors capable of sensing acceleration, vibration, or otherindicator of an applied force. Computing device 10 also includes one ormore processors 200, memory 202, a network interface 204, one or moredata storage devices 206, power source 208, one or more microphones 210,one or more speakers 212, one or more cameras 214, andpresence-sensitive display 12, which may be a touchscreen or otherpresence-sensitive display. Each of the components 222, 224, 226, 200,202, 204, 206, 208, 210, 212, 214, and 12 may be interconnected(physically, communicatively, and/or operatively) in any of a variety ofphysical and/or communicative connection means for inter-componentcommunications.

Computing device 10 has operating system 190 stored on one or morestorage devices 206, and that may execute on one or more processors 200.Operating system 190, in various examples, may control aspects of theoperation of components of computing device 10, and facilitate operationof higher-level software applications. Computing device 10, in thisexample, has applications 185 that may include a non-visual input/output(I/O) application 120 that is executable by computing device 10.Non-visual I/O application 120 may include executable instructions toperform or facilitate any or all of detecting forces applied tocomputing device 10, determining whether the applied forces match storedparameters for force-based inputs, gathering data or outputs from othersources or applications if necessary to respond to the force-basedinputs, and outputting non-visual responses to the force-based inputs,or any other aspects of this disclosure, which may collectively bereferred to as “non-visual I/O” as an abbreviated term of reference.Operating system 190, in one example, facilitates the interaction ofnon-visual I/O application 120 with any or all of accelerometer 222, acompression sensor 224, and an acoustic sensor 226, processors 200,memory 202, network interface 204, data storage device 206, power source208, one or more microphones 210, one or more speakers 212, one or morecameras 214, and presence-sensitive display 12.

As shown in FIG. 2, non-visual I/O application 120 may include an inputmodule 122 and an output module 124. Input module 122 may includeportions of executable code responsible for detecting forces applied tocomputing device 10 and determining whether the applied forces matchcorresponding force-based inputs, and output module 124 may includeportions of executable code responsible for performing the correspondingfunctions and generating non-visual outputs based on the correspondingfunctions, for example.

Non-visual I/O application 120, input module 122, and output module 124may each include program instructions and/or data that are executable bycomputing device 10 or by at least one of the one or more processors 200of computing device 10. For example, non-visual I/O application 120,input module 122, and/or output module 124 may includecomputer-executable software instructions that cause computing device 10to perform any one or more of the operations and actions described inthe present disclosure. In various examples, operating system 190 andbrowser application 120 may include code and/or data that are stored onone or more data storage devices 206 and that are read and executed orprocessed by one or more processors 200, and may in the process bestored at least temporarily in memory 202.

In this illustrative implementation of computing device 10, operatingsystem 190 may include an operating system kernel 192, which may includevarious device drivers, kernel extensions, and kernel modules, forexample. Operating system 190 may also include or interact with a set oflibraries 180, which may include various more or less standard,specialized, open source, and/or proprietary libraries. These mayinclude a specialized library, such as non-visual I/O framework 182,that may perform or support non-visual I/O functions in accordance withany of the examples described herein.

In an illustrative implementation of computing device 10, operatingsystem 190 may also include or interact with a runtime 194, which mayinclude various core libraries 196 and/or a virtual machine 198, whichmay be the Dalvik virtual machine in an example implementation. Virtualmachine 198 may abstract certain aspects and properties of computingdevice 10 and allow higher-level applications 185 to run on top ofvirtual machine 198, so that software code in the higher-levelapplications 185 may be compiled into bytecode to be executed by thevirtual machine 198. Computing device 10 may also have an applicationframework 130 that executes on top of runtime 194 and libraries 180 andthat may include resources to facilitate the execution of applications185 that execute on top of application framework 130. Other embodimentsmay include other elements of a software stack between the operatingsystem kernel 192 and the top-level applications 185.

Application framework 130 may, for example, include a non-visual I/Omanager 132 that itself may include executable instructions to performor facilitate any or all of detecting forces applied to computing device10, determining whether the applied forces match stored parameters forforce-based inputs, gathering data or outputs from other sources orapplications if necessary to respond to the force-based inputs, andoutputting non-visual responses to the force-based inputs, or any otheraspects of this disclosure. Computing device 10 may perform orfacilitate any of these or other non-visual I/O functions with any oneor all of the non-visual I/O application 120, the non-visual I/O manager132 in the application framework 130, the non-visual I/O framework 182in the libraries 180, or any other element of the software stackincluded in or operatively accessible to computing device 10.

In various examples, executable instructions for applications orsoftware elements such as non-visual I/O application 120 may be writtenin C, which may be executable as native code by computing device 10; ormay be written in Java, then compiled to virtual-machine-executablebytecode to be executed by virtual machine 198. As one illustrativeexample, libraries 180 may include the Standard C Library (libc), whichprovides native support for C functions. In different implementations,the operating system 190 and/or the virtual machine 198 may be able toexecute code written in various other languages such as Objective-C, C#,C++, Go, JavaScript, Dart, Python, Ruby, or Clojure, for example, eithernatively, or compiled into a virtual machine-executable bytecode, orcompiled into an assembly language or machine code native to the CPU ofcomputing device 10, for example. Various examples may not use a virtualmachine, and use applications that run natively on the computing device10C or that use some other technique, compiler, interpreter, orabstraction layer for interpreting a higher-level language into codethat runs natively on computing device 10.

GUI framework 182, libraries 180, or other aspect of operating system190 or the software stack underlying the applications 185 may includecode for providing any or all of the functionality for performingnon-visual I/O, e.g., detecting force-based inputs and generatingnon-visual outputs based on functions that match the correspondingforce-based inputs, in accordance with any of the examples describedabove, and may abstract this functionality at an underlying level forapplications 185. Code for implementing the functionality of any of theaspects of this disclosure may therefore be included in any level orportion of the entire software stack running on computing device 10, orthat is operatively accessible to computing device 10, such as in a webapplication or other program executing on resources outside of computingdevice 10 but that interact with computing device 10, such as via HTTPover a wireless connection, for example.

In various examples, computing device 10 may also have variousapplication programming interfaces (APIs) that are native to operatingsystem 190 and that run on top of operating system 190, and which areintended to provide resources that automate or facilitate higher-levelapplications that access the one or more APIs. These one or more APIsmay include object libraries or other libraries, toolsets, orframeworks, and may be associated with a native programming environmentfor writing applications. Computing device 10C may also have a differentspecific organization of APIs, libraries, frameworks, runtime, and/orvirtual machine associated with or built on top of operating system 190other than the example organization depicted in FIG. 2.

Higher level applications, such as non-visual I/O application 120, maytherefore make use of any of various abstractions, properties,libraries, or lower-level functions that are provided by any ofoperating system 190, OS kernel 192, libraries 180, non-visual I/Oframework 182, runtime 194, core libraries 196, virtual machine 198, orother compilers, interpreters, frameworks, APIs, or other types ofresources, or any combination of the above, with which computing device10 is configured, to enable functions such as detecting force-basedinputs and generating non-visual outputs based on functions that matchthe corresponding force-based inputs, and other functions as describedherein.

The one or more processors 200, in various examples, may be configuredto implement functionality and/or process instructions for executionwithin computing device 10. For example, processors 200 may be capableof processing instructions stored in memory 202 or instructions storedon data storage devices 206. Computing device 10 may include multipleprocessors, and may divide certain tasks among different processors. Forexample, processors 200 may include a central processing unit (CPU),which may have one or more processing cores. Processors 200 may alsoinclude one or more graphics processing units (GPUs), and/or additionalprocessors. Processors 200 may be configured for multi-threadedprocessing. Processors 200 and/or operating system 190 may divide tasksamong different processors or processor cores according to certaincriteria, such as to optimize the user experience. Various tasks orportions of tasks may also be divided among different layers of softwareand hardware.

Memory 202, in various examples, may be configured to store informationwithin computing device 10 during operation. Memory 202, in variousexamples, may be a computer-readable storage medium. In variousexamples, memory 202 is a temporary memory, and computing device 10relies more on one or more data storage devices 206 than memory 202 forlong-term storage. Memory 202, in various examples, may be a volatilememory, meaning that memory 202 may not maintain stored contents for along duration of time once it is powered down, such as when computingdevice 10 is turned off. Examples of volatile memories that maycharacterize memory 202 include random access memories (RAM), dynamicrandom access memories (DRAM), static random access memories (SRAM), andother forms of volatile memories. In various examples, memory 202 may beused to store program instructions for execution by processors 200.Memory 202, in various examples, may be used by software or applicationsrunning on computing device 10 to temporarily store data and/or softwarecode during execution of an application.

One or more data storage devices 206, in various examples, may include acomputer-readable storage medium or multiple computer-readable storagemedia. Data storage devices 206 may be configured to store largeramounts of information than memory 202. Data storage devices 206 mayfurther be configured for long-term storage of information. In variousexamples, data storage devices 206 include non-volatile storageelements. Examples of such non-volatile storage elements includemagnetic hard discs, optical discs, floppy discs, flash memories, orforms of electrically programmable memories (EPROM) or electricallyerasable and programmable (EEPROM) memories. In other examples, memory202 may also be configured for long-term data storage, and any of avariety of technologies may blur the lines between memory and datastorage and between volatile and non-volatile. Memory 202 and datastorage devices 206 may also include any of various caches, buffers, andother temporary memories that may be incorporated at any of variouslevels of a processing architecture and with various latency andcapacity profiles, including a dedicated cache exclusive to a processingcore or processing chip.

Computing device 10, in various examples, may also include a networkinterface 204. Computing device 10C, in one example, utilizes networkinterface 204 to communicate with external devices, such as servers ordata centers, via one or more networks, which may include one or morewireless networks. Network interface 204 may be or include a networkinterface card, such as an Ethernet card, an optical transceiver, aradio frequency transceiver, or any other type of component that isconfigured to send and receive information. Other examples of suchnetwork interfaces may include Bluetooth®, 3G; 4G; LTE, and WiFi® radiosconfigured for mobile computing devices, as well as USB. In variousexamples, computing device 10 may use network interface 204 tocommunicate wirelessly with an external device such as a server or datacenter that may provide data to computing device 10.

Computing device 10, in various examples, may also include one or moreinput and/or output devices such as presence-sensitive display 12C.Presence-sensitive display 12C may include a liquid crystal display(LCD) display screen or display screen that uses another type ofgraphical output technology. Presence-sensitive display 12C may also bea touchscreen, that may include an electrically capacitive layersensitive to the presence of touch and configured to translate thepositions of touch gesture inputs, and the motions of touch gestureinputs as they change position over time, into signals to provide to adriver for the touchscreen or other feature for receiving theinformation on the gesture inputs. Presence-sensitive display 12 mayalso be another type of presence-sensitive display in other examples.

Computing device 10 may also include or be configured to connect withany of a variety of other input and/or output devices such as physicalbuttons, a physical keyboard, a mouse, a touchpad, a trackball, a voiceuser interface system, a vibration component, a sound card, a videographics adapter card, or any other type of device for detecting and/orinterpreting inputs from a user or for converting a signal into a formof graphical, audio, tactile, or other form of user output that can besensed by a user.

Computing device 10C, in various examples, may include one or more powersources 208, which may be rechargeable and provide power to computingdevice 10C. Power source 208, in various examples, may be a lithium-ionbattery, a nickel-cadmium battery, a nickel-metal hydride battery, orother suitable power source.

Computing device 10 may also include one or more force-sensitive sensorssuch as accelerometer 222, compression sensor 224, acoustic sensor 226,a gyroscope, or other types of sensors capable of detectingacceleration, compression, vibration, rotation, or other indicator offorce applied to computing device 10. Accelerometer 222 may measure anyacceleration of computing device 10, and therefore detect any net forceapplied to computing device 10, including the net force from a usertapping anywhere on computing device 10, including through a pocket, ahandbag, or other intervening material. Compression sensor 224 maydetect a compressive force to computing device 10 or one or moreportions of the surface of computing device 10, and could detect anapplied force in the form of a compression or a squeezing action appliedto computing device 10. Acoustic sensor 226 could detect an appliedforce in the form of a mechanical or acoustic vibration, which mayinclude vibrations transmitted through intervening materials between asurface a user applies a force to and computing device 10. For example,computing device 10 may be positioned in a user's pocket or in awristwatch or armband form factor, and detect when the user taps anotherarea of the user's body, through acoustic vibrations transmitted fromthe tapped area through the user's body (e.g., through the user'sskeletal system) to the computing device 10. Computing device 10 mayinclude multiple accelerometers 222, compression sensors 224, and/oracoustic sensors 226, and may use one or multiple of one of these typesof sensors or one or multiple of multiple types of these sensors, any ofwhich may facilitate reliable detection and processing of suchforce-based input signals.

FIGS. 3-6 are example graphs 30, 40, 50, 60, respectively of force oracceleration over time corresponding to force-based inputs as may bedetected by an accelerometer, compression sensor, acoustic sensor,gyroscope, or other sensor operatively connected to a mobile computingdevice, in accordance with aspects of the present disclosure. Each ofgraphs 30, 40, 50, 60 shows a measure of force over time as detected bya sensor such as accelerometer 222, etc. on computing device 10. Theforce sensor may communicate the detected force data represented by thegraphs 30, 40, 50, 60 to other elements of computing device 10 of FIG.2, such as processor(s) 200, to compare the data represented by thegraphs 30, 40, 50, 60 with parameters for stored force-based inputs todetermine if the detected force data matches one of the correspondinginputs. While graphs 30, 40, 50, 60 are not labeled with units, thedetails of units for a suitable user input profile of force over timefor a force-based input may be calibrated in accordance with userinterface engineering practices, and stored parameters for force-baseduser inputs may be calibrated according to typical user behavior fortapping or other inputs and the system responses of a given computingdevice to such force-based user inputs.

FIG. 3 shows a pattern of an applied force detected by computing device10 over time that is close to zero for much of the time (including minorvibrations or ambient low-level motions), but that includes two close,distinct peaks in force at signal 32 that are consistent with a sequenceof two taps by a user on computing device 10, whether directly orthrough intervening materials. Computing device 10 may initially filterout minor motions such as those on graph 30 outside of signal 32 asbeing too small to register as a user input, so that computing device 10doesn't expend too much processing activity and power on performingsubstantial processing of force signals and process false positives asuser inputs, in some examples. If a signal for an applied force is ofthe right strength and duration to be a good candidate signal, computingdevice 10 may process the signal according to more rigorous mathematicalmethods to compare to stored parameters of user input signals, which maybe based on an analytical rules system or on a system trained by machinelearning techniques on sample user inputs, for example. Computing device10 may also perform further steps in response to a candidate signal,such as comparing other aspects of the current operating context ofcomputing device 10, such as whether a phone call is currently incomingor whether the display is activated, for example.

Computing device 10 may have one set of stored parameters for aforce-based user input of a double-tap sequence that corresponds to theapplied force signal 32 shown in FIG. 3. The particular correspondinginput, i.e., the particular corresponding set of stored parameters thatmatch the sensor data of signal 32, may be any input to any application.The particular corresponding input may also have an initial defaultinput that might be determined by the operating system 190 or bepre-selected by a vendor of computing device 10, for example, and may befreely user-configurable to any other input that a user selects. Theparticular corresponding input may also be selected differently based onthe current operating context when the signal 32 is detected, so thatthe signal 32 may be interpreted as one input in a default context, or asecond input when a new phone call is incoming, or a third input whensimultaneous data from other sensors show that the user is currentlydriving a car, for example. In particular, a default setting in adefault context might be to respond to the double-tap input of signal 32by generating an audio output of the current time and information aboutany recently received emails or text messages, for example. If a newphone call is currently incoming while the computing device 10 receivesthe double-tap input of signal 32, the default setting in this contextmay be to generate an audio output identifying the caller, for example.If the computing device 10 receives the double-tap input of signal 32while it detects that the user is currently driving a car, such as bycommunicating with the car, or by detecting motion at typical car speedsvia position sensors (e.g., GPS and/or WiFi position sensors) andrecognizing that the particular car belongs to the user, computingdevice 10 may respond by generating audio outputs for a streetnavigation voice user interface, for example. Any other correspondingfunctions and outputs may also be used or selected in any of thesecontexts for responding to the force-based user input corresponding tothe detected force of signal 32.

Similarly, any default or user-configurable function and output may beselected to correspond to other user inputs such as those represented bysignal 42 in graph 40 of FIG. 4 (corresponding to a user's sequence ofthree taps), signal 52 in graph 50 of FIG. 5 (corresponding to a usershaking the computing device 10), signal 62 in graph 60 of FIG. 6(corresponding to a single tap by the user), or other signals. Asanother example, computing device 10 may also interpret taps todifferent portions of itself as different inputs, e.g., it maydistinguish between a tap to its front or back, or to a side edge or acorner, and apply different non-visual responses based on thosedifferent inputs. Computing device 10 may differentiate among theseinputs through inputs to accelerometers in different orientations ordifferent positions within the body of computing device 10, for example.The signals shown in FIGS. 3-6 are examples, but any other type orpattern of signal may also be saved as a user input parameter and may beinterpreted as a corresponding user input. Other examples may alsoincorporate signals from various types of force-based sensors, such as asignal corresponding to one or more squeezes or compressions of one ormore compression sensors. Regarding a detected force corresponding to asingle tap as in FIG. 6, computing device 10 may in some examples applydefault responses to this input only in special operating contexts suchas during an incoming phone call (e.g., when the phone is ringing), butapply no action in a default operating context, since a single,temporary force may be likely to arise from time to time from ordinarymotions, so that avoiding a response in ordinary contexts helps preventinterpreting ambient motions as false positives when they are not inputsintended by the user.

FIG. 7 depicts computing device 10 with graphical user interface (GUI)20 and outputting GUI content for a representative portion of an exampleuser configuration interface 22 for non-visual I/O application 120 thatgenerates non-visual outputs in response to force-based inputs, inaccordance with aspects of the present disclosure. Computing device 10renders GUI 20 on presence-sensitive display 12, which may be atouchscreen. As shown on presence-sensitive display 12, userconfiguration interface 22 includes a variety of operating contexts, anda variety of force-based user inputs listed under each operatingcontext, along with the corresponding non-visual output functions thatmay be assigned to each corresponding force-based input. As shown inFIG. 7, the example settings currently depicted by user configurationinterface 22 include a default context and an “incoming call” context.As further shown in FIG. 7, non-visual output functions assigned tovarious force-based inputs under the default context include an audiooutput of the current time for a single tap (corresponding to detectedforce signal 62 in FIG. 6); an audio output of information aboutrecently received phone calls, text messages, and emails, correspondingto a double tap input (corresponding to detected force signal 32 in FIG.3); and an audio output of information about pending calendar items inresponse to a triple tap input (corresponding to detected force signal42 in FIG. 4). FIG. 7 also shows that a single squeeze input and a shakeinput under the default context are currently unassigned, and that asingle tap under the context of a currently incoming phone call isassigned to generate an audio output identifying the caller.

User configuration interface 22 may also scroll down to reveal manyadditional input/output assignments under the incoming phone callcontext or any of various other operating contexts. User configurationinterface 22 may also include options for the user to add additionalinputs and assign corresponding functions and outputs. The user may beenabled to select additional inputs from a list, or to define a newforce-based input kinematically with the computing device 10 recordingwhatever pattern of force the user applies to it, to generate a newuser-defined force-based input. Computing device 10 may also enable theuser to define any non-visual output to be generated in response to aselected input, and may provide tools to allow a user to integratefunctions of any application with the non-visual I/O system of thisdisclosure and assign any function of any application as an output withwhich the non-visual I/O system integrates and generates in response toa force-based user input.

For one or more pre-stored or user-defined non-visual I/O selections,computing device 10 may store a plurality of force parameters associatedwith a plurality of force inputs, such that determining that thedetected force matches the corresponding input comprises comparing thedetected force with force signal parameters associated with theplurality of force inputs, such as described with reference to FIGS.3-6.

Computing device 10 may also enable a variety of one or more additionalinputs indicating various additional operating contexts to bedifferentiated and determined in conjunction with the force-based input.Computing device 10 may also receive an indication of the one or moreadditional inputs within a defined interval of time of receiving theindication of the detected force applied to computing device 10, andgenerate a non-visual output based at least in part on the one or moreadditional inputs. For example, computing device 10 may detect if thereis an input from a presence-sensitive display indicating a large area ofcontact with the presence-sensitive display, such as if the user isapplying her palm or a large area of her hand to the touchscreen toapply a tap, which may for example be a useful additional indicator ofthe user's intention of entering force-based inputs. As another example,computing device 10 may detect an input from a light sensor anddetermine if the light sensor input indicates a level of light below aselected threshold. Computing device 10 may then apply a differentoperating context for the user being in the dark, such as when the useris in bed at night. An example differentiated I/O response in thiscontext might be to interpret a selected force-based input to mute thecomputing device 10, or to generate an audio output confirming that analarm is on and the time for which it is set, for example.

As another example of shifting non-visual I/O responses by operatingcontext, computing device 10 may compare input from a magnetic fieldsensor and apply different non-visual outputs based on a direction oftravel indicated by the magnetic field sensor, such as during a voiceuser interface navigation function. As another example, computing device10 may detect one or more additional inputs from a near-fieldcommunication (NFC) tag sensor, and modify the non-visual I/O responsesbased on the NFC tag detected.

Additionally, any of a wide variety of non-visual outputs may begenerated in response to a force-based user input. Some examples may usea force input to initiate a voice user interface so the user may tap thecomputing device and then issue a speech input, and the computing devicemay respond with an audio output, including for functions involvingsearch and navigation. In this case, the computing device may detect thespeech input as part of performing the corresponding function inresponse to detecting the corresponding force-based user input thatinitiates the voice user interface mode. For example, computing device10 may receive a speech input and perform a speech-to-text function onthe speech input to generate a text query based on the speech input. Inone example, computing device 10 may then enter the text query to asearch application, wherein generating the non-visual output comprisesgenerating a speech synthesis audio output of the results of the websearch. As another example, computing device 10 may then determine acurrent location based at least in part on one or more position sensors,and perform a location-based search based at least in part on the textquery and on the current location, wherein generating the non-visualoutput comprises generating a speech synthesis audio output of theresults of the location-based search. As yet another example, computingdevice 10 may then determine a current location based at least in parton one or more position sensors, and perform, with a navigationapplication, a location-based navigational route search based at leastin part on the text query and on the current location, whereingenerating the non-visual output comprises generating a speech synthesisaudio output of the results of the location-based navigational routesearch.

Computing device 10 may also issue any of a variety of other non-visualoutputs, drawing on any of a variety of applications, data sources, orother resources. For example, computing device 10 may generate a speechsynthesis audio output of news using data from a news application, or offinancial information using data from a financial data application, orwith identifying information about an incoming phone call using datafrom a telephone application. Computing device 10 may apply variousother forms of receiving a speech input, performing a speech-to-textfunction on the speech input to generate a text based on the speechinput, and entering the text to an application, to elicit some form ofresponsive output or data from the application based on the speechinput.

Computing device 10 may also apply a variety of location-based functionsin non-visual I/O responses. For example, computing device 10 mayexecute a corresponding function in response to detecting a force-baseduser input where the corresponding function includes determining acurrent location based at least in part on one or more position sensors,and performing an additional function or generating an output based inpart on the location. This may include starting or stopping a recordedtrack at the current location in a route tracking application, providinglocal advertising content relevant to the current location, providing auser check-in to the current location in a location-based socialnetworking application, or marking the current location in a geocachingapplication, for example.

Computing device 10 may also record and enter speech inputs to any of avariety of applications as part of executing a corresponding function inresponse to detecting a force-based user input. This may includeinteraction with an email application, a text message application, or aword processing application, for example. The computing device 10 mayperform additional functions such as sending an email or a text messagecomprising the entered text based on the speech input, or saving thetext in a word processing file, for example.

FIG. 8 is a flow diagram illustrating an example process 300 or methodthat may be performed by or be embodied in a computing device, such ascomputing device 10 of FIGS. 1,2, and 7, and/or any one or moreprocessors thereof, to implement a non-visual I/O system to generatenon-visual outputs in response to inputs that correspond to detectedforces, in accordance with any of the examples described above. Process300 is only one example, and other implementations may include more orfewer aspects than those depicted in FIG. 8.

In process 300, a computing device 10 or processor(s) 200 thereof mayexecute instructions, such as those of non-visual I/O application 120.In this example, a sensor (e.g., accelerometer 222, compression sensor224, acoustic sensor 226) of computing device 10 or that is operativelyconnected to computing device 10 detects a force applied to thecomputing device 10, and conveys a digital signal or other data thatindicates that detected force. Computing device 10 or processor(s) 200receives this indication of a force applied to computing device 10(302). Computing device 10 or one or more processor(s) 200 of computingdevice 10 determines that the detected force matches a correspondinginput that computing device 10 associates with a corresponding functionthat is executable by computing device 10 (304). For example, thedetected force may be characterized by force parameters that areconsistent with a user tapping, squeezing, or shaking computing device10, with one or more taps, squeezes, or shakes, and which may be withinan interval of time of each other. Computing device 10 may associatedifferent force inputs with different force parameters with differentcorresponding functions, so that each of the corresponding functions maybe indicated by a different force input, as described above withreference to FIGS. 3-7. Computing device 10 or one or more processor(s)200 then generates, in response to determining that the detected forcematches the corresponding input, a non-visual output based on thecorresponding function (306). The computing device may further performany of the functions and processes described above with reference toFIGS. 1-7.

Various techniques described herein may be implemented in software thatmay be written in any of a variety of languages, making use of any of avariety of toolsets, frameworks, APIs, programming environments, virtualmachines, libraries, and other computing resources, as indicated above.For example, software code may be written in Java, C, Objective-C, C++,Go, JavaScript, Dart, Python, Ruby, Clojure, assembly language, machinecode, or any other language. As one specific illustrative example,aspects of the disclosure discussed above may be implemented in asoftware module written in Java that is executable on virtual machine198 of FIG. 7, for example.

Aspects of the disclosure may be equally applicable and implemented inany computing device or any operating system, and using any other APIs,frameworks, or toolsets. Aspects described herein for decoding andprocessing of data for force-based inputs and non-visual outputs, whichmay interact with any other data store or application. When implementedin software or firmware, various techniques disclosed herein may berealized at least in part by a computer-readable data storage mediumcomprising instructions that, when executed, cause a processor toperform one or more of the methods described above. For example, thecomputer-readable data storage medium may store such instructions forexecution by a processor.

A computer-readable medium may form part of a computer program product,which may include packaging materials. A computer-readable medium maycomprise a computer data storage medium such as random access memory(RAM), read-only memory (ROM), non-volatile random access memory(NVRAM), electrically erasable programmable read-only memory (EEPROM),flash memory, magnetic or optical data storage media, and the like. Invarious examples, an article of manufacture may comprise one or morecomputer-readable storage media.

In various examples, the data storage devices and/or memory may comprisecomputer-readable storage media that may comprise non-transitory media.The term “non-transitory” may indicate that the storage medium is notembodied in a carrier wave or a propagated signal. In certain examples,a non-transitory storage medium may store data that can, over time,change (e.g., in RAM or cache). Data storage devices may include any ofvarious forms of volatile memory that may require being periodicallyelectrically refreshed to maintain data in memory, but those skilled inthe art will recognize that this also constitutes an example of aphysical, tangible, non-transitory computer-readable data storagedevice. Executable instructions are stored on a non-transitory mediumwhen program code is loaded, stored, relayed, buffered, or cached on anon-transitory physical medium or device, including if only for only ashort duration or only in a volatile memory format. Machine-readablecode may be stored on the data storage devices and/or memory, and mayinclude executable instructions that are executable by at least oneprocessor. “Machine-readable code” and “executable instructions” mayrefer to any form of software code, including machine code, assemblyinstructions or assembly language, bytecode, software code in C, orsoftware code written in any higher-level programming language that maybe compiled or interpreted into executable instructions that may beexecutable by at least one processor, including software code written inlanguages that treat code as data to be processed, or that enable codeto manipulate or generate code.

The code or instructions may be software and/or firmware executed byprocessing circuitry including one or more processors, such as one ormore digital signal processors (DSPs), general purpose microprocessors,application-specific integrated circuits (ASICs), field-programmablegate arrays (FPGAs), or other equivalent integrated or discrete logiccircuitry. Accordingly, the term “processor,” as used herein may referto any of the foregoing structure or any other structure suitable forimplementation of the techniques described herein. In addition, in someaspects, functionality described in this disclosure may be providedwithin software modules or hardware modules.

The various embodiments described above and depicted in FIGS. 1-8, aswell as additional embodiments, are within the scope of one or more ofthe following claims.

1-20. (canceled)
 21. A method comprising: receiving, by a computingdevice, an indication of a detected force applied to at least a portionof the computing device; determining, by the computing device, that thedetected force matches a corresponding input that the computing deviceassociates with a corresponding function to be performed by thecomputing device; receiving, by the computing device, a user input;after determining that the detected force matches the correspondinginput, performing, by an application executing on the computing device,and based at least in part on the user input, the correspondingfunction; and generating, by the computing device and based at least inpart on performance of the corresponding function by the application, anaudio output.
 22. The method of claim 21, further comprising:determining, by the computing device, that the detected force is appliedto at least the portion of the computing device while apresence-sensitive display operatively connected to the computing deviceis in a deactivated state, wherein generating the audio output isresponsive to determining that the detected force is applied to at leastthe portion of the computing device while the presence-sensitive displayis in the deactivated state.
 23. The method of claim 21, whereinreceiving the indication of the detected force comprises receiving theindication of the detected force from a sensor operatively connected tothe computing device, the sensor comprising at least one of anaccelerometer, a compression sensor, or an acoustic sensor.
 24. Themethod of claim 21, wherein determining that the detected force matchesthe corresponding input that the computing device associates with thecorresponding function to be performed by the computing device comprisesdetermining a strength and a duration of the detected force.
 25. Themethod of claim 21, further comprising: receiving, by the computingdevice, an indication of one or more additional inputs within a definedinterval of time of receiving the indication of the detected forceapplied to at least the portion of the computing device, whereingenerating the audio output is further based at least in part on the oneor more additional inputs.
 26. The method of claim 25, wherein the oneor more additional inputs comprise at least one of: an input from aposition sensor indicating at least one of a position or a velocity ofthe computing device; an input from a network interface indicating atleast one of the position or the velocity of the computing device; aninput from a Global Positioning System interface indicating at least oneof the position or the velocity of the computing device; an input from alight sensor indicating a level of light; or an input from a magneticfield sensor indicating at least one of the velocity or an orientationof the computing device.
 27. The method of claim 21, wherein thecorresponding function performed by the application comprises a search,and wherein generating the audio output comprises generating a speechoutput of at least one result of the search performed by theapplication.
 28. The method of claim 27, further comprising:determining, by the computing device, and based at least in part oninformation from one or more position sensors, a current location of thecomputing device, wherein the search comprises a location-based searchbased at least in part on the current location of the computing device.29. A computing device, comprising: at least one processor; at least onesensor; and a non-transitory computer-readable storage mediumcommunicatively coupled to the at least one processor, wherein thecomputer-readable storage medium stores instructions that, whenexecuted, cause the at least one processor to: receive, from the atleast one sensor, an indication of a detected force applied to at leasta portion of the computing device; determine that the detected forcematches a corresponding input that the at least one processor associateswith a corresponding function to be performed by the at least oneprocessor; receive a user input; after determining that the detectedforce matches the corresponding input, perform, by an application, andbased at least in part on the user input, the corresponding function;and generate, based at least in part on performance of the correspondingfunction by the application, an audio output.
 30. The computing deviceof claim 29, further comprising a presence-sensitive display, whereinthe instructions stored by the computer-readable storage medium furthercause the at least one processor to: determine that the detected forceis applied to at least the portion of the computing device while thepresence-sensitive display is in a deactivated state; and generate, inresponse to determining that that the detected force is applied to atleast the portion of the computing device while the presence-sensitivedisplay is in the deactivated state, the audio output.
 31. The computingdevice of claim 29, wherein the at least one sensor comprises one ormore of an accelerometer, a compression sensor, or an acoustic sensor.32. The computing device of claim 29, wherein the instructions stored bythe computer-readable storage medium cause the at least one processor todetermine that the detected force matches the corresponding input thatthe computing device associates with the corresponding function to beperformed by the computing device at least by determining a strength anda duration of the detected force.
 33. The computing device of claim 29,wherein the instructions stored by the computer-readable storage mediumfurther cause the at least one processor to: receive an indication ofone or more additional inputs within a defined interval of time ofreceiving the indication of the detected force applied to at least theportion of the computing device; and generate the audio output furtherbased at least in part on the one or more additional inputs.
 34. Thecomputing device of claim 29, wherein the corresponding functionperformed by the application comprises a search, and wherein theinstructions stored by the computer-readable storage medium furthercause the at least one processor to generate the audio output at leastby generating a speech output of at least one result of the searchperformed by the application.
 35. A non-transitory computer-readablestorage medium comprising instructions that are executable by at leastone processor of a computing device to perform operations comprising:receiving an indication of a detected force applied to at least aportion of the computing device; determining that the detected forcematches a corresponding input that the computing device associates witha corresponding function to be performed by the computing device;receiving a user input; after determining that the detected forcematches the corresponding input, performing, by an application, andbased at least in part on the user input, the corresponding function;and generating, based at least in part on performance of thecorresponding function by the application, an audio output.
 36. Thenon-transitory computer-readable storage medium of claim 35, wherein theoperations further comprise: determining that the detected force isapplied to at least the portion of the computing device while apresence-sensitive display operatively connected to the computing deviceis in a deactivated state, wherein generating the audio output isresponsive to determining that the detected force is applied to at leastthe portion of the computing device while the presence-sensitive displayis in the deactivated state.
 37. The non-transitory computer-readablestorage medium of claim 35, wherein the operations further comprisereceiving the indication of the detected force from a sensor operativelyconnected to the computing device, the sensor comprising at least one ofan accelerometer, a compression sensor, or an acoustic sensor.
 38. Thenon-transitory computer-readable storage medium of claim 35, whereindetermining that the detected force matches the corresponding input thatthe computing device associates with the corresponding function to beperformed by the computing device comprises determining a strength and aduration of the detected force.
 39. The non-transitory computer-readablestorage medium of claim 35, wherein the operations further comprise:receiving an indication of one or more additional inputs within adefined interval of time of receiving the indication of the detectedforce applied to at least the portion of the computing device, whereingenerating the audio output is further based at least in part on the oneor more additional inputs.
 40. The non-transitory computer-readablestorage medium of claim 35, wherein the corresponding function performedby the application comprises a search, and wherein generating the audiooutput comprises generating speech output of at least one result of thesearch performed by the application.